Nways Manager for Windows NT Installation Guide

Post-Installation and Maintenance Procedures

This chapter provides the final steps necessary to configure Nways Manager to function properly. In addition, it explains how to make adjustments which will allow Nways Manager to continue to change along with your network.

Extracting the JDBC Drivers

Prior to creating a DB2 Database, the Java DataBase Connectivity (JDBC) drivers must be unzipped into the Nways Manager java\websvr\code directory (folder). Follow these steps to extract the drivers:

1. Obtain an unzip program (You can use the pkunzip utility that you downloaded with the DB2 FixPak).
2. Extract db2java.zip file from the Sqllib\java\ directory into the Nways\java\websvr\code directory.

Creating a DB2 Database for JPM and Starting Data Collection

After making sure that the JDBC drivers are installed and DB2 is started, follow these steps to create a database:

1. Select Start -> Programs -> MS-DOS prompt.
2. Change the directory to nways\bin.
3. Run the command db2cmd CreateDatabase.bat -create.

   By default, a database will be created on the same disk that DB2 was installed. It is advised that this disk partition have at least 60 to 100 MB of free disk space. If you intend to store historical statistics for more than 20 devices over a period several weeks or longer, then you will need approximately 1 GB or more of available disk space.

4. Depending on your platform:
   • Start NetView by selecting Start -> Programs -> NetView -> NetView Console.
   • Start OpenView by selecting Start -> Programs -> OpenView -> Network Node Manager.
5. Select Tools -> IBM Nways Java -> Performance Configuration.
6. Click on the Database tab.

   If you are using HP OpenView Network Node Manager on Windows NT, then you may be asked to enter your username and password. If so, enter the administrative password that you created at the beginning of this process.

7. Click Start Collection.

Potential Problems Connecting to a JDBC-enabled Database

If you encounter problems connecting to the JDBC-enabled database from Nways Manager, try the following solutions.

Message:	Could not find JDBC driver classes. Closing connection.
Action:	Install or reinstall the JDBC drivers. For DB2, unzip the JDBC drivers (found in Sqllib\java\db2java.zip where Sqllib is the default directory into which DB2 was installed) into nways\java\websvr\code, where nways is the directory into which Nways Manager was installed. You may have to retrieve an unzip program from the Internet to perform this task. For other databases, refer to the documentation for those databases. The JDBC drivers must exist in the Nways classpath (nways\java\websvr\code, where nways is the directory into which Nways Manager was installed) to allow connection to the database.
Message:	JDBC connect error. Check database URL and make sure your username and password are correct. Closing connection.
Action:	Check to make sure your database system and JDBC drivers are JDBC-compliant. The database must support ANSI-92 SQL. Check the JDBC URL and make sure it is the one that the database manufacturer suggests you use. This can usually be found in the database documentation under a section dealing with running Java applications. If you are using a third-party driver, then the URL and driver name should be included with that driver. the default URL is given for the DB2 running locally. Make sure you have created a database called IBMNMPDB. If you are not using DB2, read your database documentation on how to do this. If you are using DB2, change to the directory nways\bin, where nways is the directory into which Nways Manager was installed, and run the command: db2cmd CreateDatabase.bat -create Make sure that the disk on which you have created the database has at least 60 to 100MB of space. The exact amount of space required depends on how much historical information will be stored The following databases and JDBC drivers are known to be incompatible with Nways Manager and are not recommended: Microsoft Access, JDBC-ODBC Bridge.

Clearing out the DB2 Database

After a period of use, it may be necessary to clear out the DB2 database. To clean out the database, change to the directory nways\bin, where nways is the directory into which Nways Manager was installed, and run the command: db2cmd CreateDatabase.bat -create

Editing the Seed File

Tivoli NetView IT Director Edition Version 5.1's default only discovers devices within one hop of the machine running NetView. In order to discover others, follow these steps to edit the seed file:

1. Start NetView by selecting Start -> Programs -> NetView -> NetView Console.
2. Select Options -> Discovery....
3. Select the Discover with Seed File check box.
4. Click Edit.
5. Add Seed IP address to the bottom of the file (the default seed file contains instructions).
6. Select File -> Save.
7. Close the Notepad window.
8. Click Edit to the right of the Use Alternative Community Names in File field.
9. Add any additional Community Names to the bottom of the file (the default community names file contains instructions).
10. Select File -> Save.
11. Close the Notepad window.
12. Change the Discovery Speed field from Medium to High Initially.
13. Click Apply.
14. Click Yes.
15. Click OK.
16. Double click the IP Internet icon in the Root map. Nodes will appear on the map as they are polled. Blue squares in the Network Polling Activity box indicates that polling is in progress, while red squares mean that a poll is pending.

To refresh the Nways Device Management map, select Tools -> IBM Nways Java -> Refresh Nways Map.

Managing Licenses

As part of the installation process, you are asked whether or not you want to install a licensed product or a trial version of Nways Manager. If you elect to install a trial version of the product, all Nways Manager components will be installed with a demonstration license good for 60 days following installation. You can upgrade to a licensed version of Nways Manager at any time without losing your accumulated data.

If you select a licensed product, you will be prompted to enter your customer number and license key number, and then the number of nodes for which you have purchased a license.

Enter this information and click OK to continue the installation.

Upgrading Licenses

To upgrade from the demonstration version to the licensed version of Nways Manager, you must restart the installation program to install the license.

Note:

No new code will be installed and your existing configuration will be preserved.

Increasing the Number of Licensed Nodes

If you have purchased a license allowing you to manage additional nodes using Nways Element Manager or Nways Manager Suite, use the following procedure from the NetView console to update the node-count associated with your product license:

1. Select Tools -> IBM Nways Java -> Open License Status from the NetView menu bar.
2. Select Update from the License Status panel to invoke the Update panel.
3. Enter the value for the updated number of licensed nodes (enter 9999 if you have a license for an unlimited number of nodes).
4. Select Update Now to save the new value.
5. Click Close to return to the License Status panel.
6. You can click Refresh at the bottom of the License Status panel to see the updated values.

   Click the Close button to exit the License Status panel.

Determining What Nodes to Monitor

Nways Manager determines what nodes to monitor by the contents of the file nwaysjma.ini. To remove nodes that you do not want to monitor and thus increase the number of other nodes you can monitor with your current license, you can edit this file and remove their entries. To edit the file, access the IBM Nways Manager group and select Edit nwaysjma.ini.

To add nodes that you do want to monitor, edit the file and create entries for them. To do this, you must know their System Object Identifier (SYSOID).

A copy of this file is created in the c:nways/bin directory, where c is the target drive of the installation. The file is created with the installation and is given the filename original.nwaysjma.ini. To revert to your original configuration, rename this file nwaysjma.ini.

Accessing Java-based Management Applications from a Web Browser

There are three components involved in Web browser-based access to the Java-based management applications:

The Nways Manager Workstation

The Nways Manager Workstation maintains the Nways Manager web pages that are sent from the web server to the web browser clients.

The Web Server

The Web server provides the Nways Manager web pages to the web browser clients when requested. The web server does not need Java support, it sees the Nways Manager web pages as data files. It is recommended that the web server be located on the same workstation as the Nways Manager workstation.

The JDK 1.1.6-compliant Web Browser Client

The web browser client requests the Nways Manager web pages from the Web servers.

In order to utilize all the functions of Nways Nways Manager, you will need a JDK 1.1.6-compliant browser. However, to view the JMA help or the reports generated by the Java Performance Manager, you can use any web browser.

The Web Server

In order to make the Nways Manager web pages available to the web browser clients, you will need to associate the Nways Manager web pages with a logical directory name in your web server. Most web servers allow you to specify the logical directory name (for example, Nways) using its administration program. The Nways Manager web pages are located in nways\java\websvr on the Nways Manager, where nways is the directory in which you installed Nways Manager.

Settings

All Web Servers must be configured to communicate with the client on port 80, which is the default port in most Servers. The following sections define the required settings for some common Web Servers.

Apache Web Server

Add the following lines, in this order, to the file \Server_root\conf\srm.conf:

Alias \nways      "\Nways\java\websvr"
Alias \cgi\code   "\Nways\java\websvr\code"
ScriptAlias \cgi  "\Nways\java\websvr"

Where Server_root is the directory in which Apache Websvr is installed, and Nways is the directory where the Nways product is installed.

Netscape Web Server

1. Go to the server main page to verify that the server is on.
2. Select the Programs menu from the menu bar.
3. Select CGI File Type.
4. Select Yes to activate CGI as a file type.
5. Select Content Management from the menu bar.
6. Select Additional Document Directories, and add the following lines:

   URL prefix: nways
   Map To Directory: \Nways\java\websvr
    
   URL prefix: cgi
   Map To Directory: \Nways\java\websvr
   

Domino Web Server

1. Go to http://Machine/Frntpage.html, where Machine is the directory in which you installed the Domino Web Server.
2. Select Configuration and Administration Forms, which will take you to http://Machine/admin-bin/Cfgin/initial.
3. Select Request Routing, which will take you to http://Machine /admin-bin/Cfgin/mpfrule.
4. Add the following lines in this order:

   Action     Request Template      Replacement File Path
   ------     ----------------      ---------------------
   Pass       \nways\*           \Nways\java\websvr\*
   Exec       \cgi\CgiLauncher*  \Nways\java\websvr\CgiLauncher*
   Pass       \cgi\*             \Nways\java\websvr\*
   

The JDK 1.1.5-Compliant Web Browser

Java support comes with your browser.

Note:

If you are using Microsoft Internet Explorer Version 4.x or 5.x, then you must update the Java Virtual Machine by selecting other options at the Web site: http://www.microsoft.com/windows/ie/download/default.asp You will also need to download the RMI patch from the same site.

For information on configuring your browser for use with Nways Manager, detailed instructions are contained in the file: nways\java\websvr\help\ibm.nways.subsys.webtoc.html. Nways is the directory where Nways Manager is installed.

After configuring your browser, you can access the Java-based management applications for your devices by specifying the URL for the Nways Manager HTML pages to the web browser.

Accessing the Java-based Management Application Helps

The Java-based management applications use a Web browser to display their HTML help panels. The Nways Manager install program will attempt to locate your default browser by looking in the NT registry. If it finds one it recognizes, it will tell Nways Manager to use it.

If it cannot locate a browser it recognizes, then it will issue a warning message requiring you to specify the path in the nways\java\websvr\properties\BrowserApplet.txt file. Specify the fully qualified name for the web browser on the "webBrowser.path=" line, where nways is the directory in which Nways Manager is installed.

About Device Configuration Programs

Some IBM networking devices include a configuration program. Nways Manager allows you to launch these configuration programs from the device's JMA.

In order to launch the configuration program from the JMA, Nways Manager must know the location of the configuration tool on the Nways Management Workstation. For configuration tools shipped after July 1998, this information is added to the program registry when the configuration tool is installed.

To locate older versions of configuration tools, Nways Manager includes the Config Tool Locator, which locates existing versions of configuration tools already installed on the Nways Management Workstation. You should run the Config Tool Locator when you install Nways Manager, and again after each installation of a configuration tool that originally shipped prior to July 1998.

To run the Config Tool Locator from the Start menu, select Programs -> IBM Nways Manager -> Config Tool Locator.

If the Config Tool Locator is unable to find a configuration tool that is loaded on the Nways Management workstation, you can add the location of the program to the registry using the following procedure:

1. Locate the correct configuration tool (cfg.exe or cfg.app file) on the path nways/java/fixcfg, and note the file size.
2. Check the Config Tool Locator's FixCfg.properties file to ensure that the file size of this configuration tool is unique.
3. Add a new entry to the FixCfg.properties file, using existing entries as models.
4. Rerun the Config Tool Locator.
5. Restart the JMA.

Nways Deployment Manager

Nways Deployment Manager is one of the components installed with Nways Manager for Windows NT. When you initially start Nways Deployment Manager, you will have to create a DB2 database named CFGMAN. Follow these steps to create the database and open Nways Deployment Manager for the first time:

1. Click Start -> Settings -> Control Panel.
2. Double click the Services icon.
3. Find and select the DB2 Security Server entry in the Service column.
4. Confirm that the Status is Started. If the Status is not Started, then click the Start button.
5. In the same entry, confirm that the Startup is Automatic. If the Startup is not Automatic, then click the Startup... button and change the Startup Type to Automatic.
6. Click Start -> Programs -> Command Prompt.
7. Type ovstop JMAintegrator.
8. Click Start -> Programs -> DB2 -> Administration Tools -> Control Center.
9. Click Systems -> [your computer name] -> Instances -> DB2 -> Databases.
10. Right click on Databases and select Create -> New.
11. Follow the SmartGuide and create a database named CFGMAN
12. At the Command Prompt, type ovstart JMAintegrator.
13. Launch Nways Deployment Manager by clicking Start -> Programs -> IBM Nways Manager -> Launch Deployment Manager.

After the initial database creation, you can launch Nways Deployment Manager from the Tivoli NetView IT Director Edition Version 5.1 main menu, by selecting Tools -> IBM Nways Java -> Open Deployment Manager. For more information on this component, see the Nways Deployment Manager User's Guide.